<HTML><HEAD><TITLE>remote_yield(+Peer)</TITLE>
</HEAD><BODY>[ <A HREF="index.html">External Interface</A> | <A HREF="../../index.html">Reference Manual</A> | <A HREF="../../fullindex.html">Alphabetic Index</A> ]
<H1>remote_yield(+Peer)</H1>
Explicitly yield to the remote peer Peer
<DL>
<DT><EM>Peer</EM></DT>
<DD>Remote peer (atom)
</DD>
</DL>
<H2>Description</H2>

   <P> 
   If Peer is a valid current remote peer, this predicate will cause the control to be
   transfer to that peer, i.e. the ECLiPSe will yield to the remote
   side. This predicate returns when ECLiPSe side resumes control.
   If the remote side initiates disconnection while it has control,
   remote_yield/1 will abort after the disconnection.

<H3>Modes and Determinism</H3><UL>
<LI>remote_yield(+) is semidet
</UL>
<H3>Fail Conditions</H3>
Peer is not a valid current remote peer.
<H3>Exceptions</H3>
<DL>
<DT><EM>(peer_abort_disconnected) </EM>
<DD>Peer has disconnected.
<DT><EM>(peer_abort_error) </EM>
<DD>Some internal error has occured (this should be reported as an ECLiPSe bug to the ECLiPSe team).
</DL>
<H2>See Also</H2>
<A HREF="../../kernel/externals/remote_connect-3.html">remote_connect / 3</A>, <A HREF="../../kernel/externals/remote_disconnect-1.html">remote_disconnect / 1</A>
</BODY></HTML>
